🌱 Add release github workflow #2161
Conversation
Now that the release workflow is working for IPAM, we could add it to CAPM3. Signed-off-by: Huy Mai <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
metal3-io-bot
added
the
size/L
|
We were supposed to add it after 1.9 so we can iron out all the issues to avoid fixing multiple repos. I don't think we have a single clean run in IPAM yet, nor have done patch releases with it etc. We also agreed to make reusable workflow in project-infra before taking it in other repos. |
metal3-io-bot
added
the
do-not-merge/hold
My intention is to have this in if we have IPAM release working. In case it doesn't work out, we should fix this PR and then test it out. IMO without taking this into use in other repos, it will take a long time to have a fully working solution. The current setup in IPAM only fails in the build image step, which can be relatively easy to patch. |
Can we then patch it right now? We'll have IPAM 1.9.1 tomorrow (after CAPI 1.9.1 bump and k8s 1.32.0 bump), so thats opportunity to fix both image build and test patch release. If those pass, then we can either generalize the workflow and then it in CAPM3 and BMO as well. If it still doesn't work, I don't want to merge broken automation and then fix it three times in different repos many times. |
metal3-io-bot
added
the
needs-rebase
|
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Now that the release workflow is working for IPAM, we could add it to CAPM3.